Add com.taskade-mcp - #298

Change Type

• Add a new server definition
• Update an existing server definition
• Fix a bug in an existing definition
• Other (describe in Summary)

Summary

Adds Taskade's hosted MCP server so McpMux users can connect to Taskade workspaces, projects, and tasks over Streamable HTTP.

I work at Taskade.

Server Details

• Server Name: Taskade
• Server ID: com.taskade-mcp
• Transport: http
• Authentication: oauth
• Categories: productivity
• Upstream Repository: https://github.com/taskade/mcp

Checklist

CI-enforced — your PR will fail without these

• JSON file lives at servers/<id>.json
• Filename matches the id field exactly
• Required fields present: id, name, transport
• pnpm validate servers/<id>.json passes
• pnpm check-conflicts passes (no duplicate IDs or aliases)
• pnpm test passes
• Every commit is signed off — git commit -s (DCO)

Reviewer quality bar

• description is one clear sentence — no marketing fluff
• At least one category from categories.json is assigned
• Every ${input:ID} placeholder has a matching metadata.inputs[].id
• Every secret / credential input is marked "secret": true
• Each credential input has an obtain block with step-by-step instructions (numbered, \n between steps)
• auth.type is consistent with how credentials are actually wired into the transport
• links.repository resolves (when the upstream is public)
• capabilities (tools / resources / prompts / read_only_mode) reflect what the server actually implements
• platforms is accurate — don't claim ["all"] without verifying Windows/macOS/Linux

Platform-managed fields — leave unset

• I did not set badges, stats, sponsored, featured
• I did not set publisher.official, publisher.verified, publisher.domain_verified
• I did not add any _platform*-prefixed keys

Trademark & branding

• No "official" / "certified" / "endorsed" wording unless I represent the trademark owner
• I have the right to reference the logo URL (an asset I'm allowed to hot-link — emoji are not accepted)

Tested locally (recommended for new servers)

• Installed the server in McpMux and it started successfully
• Confirmed https://www.taskade.com/mcp is live and that an unauthenticated initialize returns 401 until OAuth completes

Notes for Reviewers

• I work at Taskade. Contact: hello@taskade.com
• Hosted endpoint: https://www.taskade.com/mcp (OAuth 2.0 PKCE). An unauthenticated initialize 401 is expected.
• The contributor schema is oneOf stdio or http, so this definition is hosted-only. Local stdio is npx -y @taskade/mcp-server from https://github.com/taskade/mcp
• Official MCP registry id: io.github.taskade/mcp-server
• Searched servers/*taskade* and the repo for "taskade" before opening this — no existing listing.

Made with Cursor